Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: eddc80a5f15d1bb38421a8dfb0670581b436c2613e4e092ad99fd35dedc5f0bb

Tx prefix hash: abd9d76e0aaa26c0717437fa954098540460360998d7a0d82b6ad05696bed241
Tx public key: a36ac2c83c8825b0c911d89604c163fcee87664ddbd9c63b94c84b23d3ff83e6
Timestamp: 1672726598 Timestamp [UCT]: 2023-01-03 06:16:38 Age [y:d:h:m:s]: 02:015:17:09:47
Block: 666495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 533141 RingCT/type: yes/0
Extra: 01a36ac2c83c8825b0c911d89604c163fcee87664ddbd9c63b94c84b23d3ff83e602110000000152542ceb000000000000000000

1 output(s) for total of 3.798615641000 dcy

stealth address amount amount idx
00: c1ca18c1f5d6b8e91384c496d231fb68c7e591f6ded4b22375e01b94d4262f1d 3.798615641000 1107606 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 666505, "vin": [ { "gen": { "height": 666495 } } ], "vout": [ { "amount": 3798615641, "target": { "key": "c1ca18c1f5d6b8e91384c496d231fb68c7e591f6ded4b22375e01b94d4262f1d" } } ], "extra": [ 1, 163, 106, 194, 200, 60, 136, 37, 176, 201, 17, 216, 150, 4, 193, 99, 252, 238, 135, 102, 77, 219, 217, 198, 59, 148, 200, 75, 35, 211, 255, 131, 230, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8