Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c65260b3549b9b8d23b498870444f0b1a017a01e8ccb7327e3e66d455dac2f4

Tx prefix hash: e636f1b363261acbd1279094f5527e082fc9a0fe1640e803bb94f60e7659a20a
Tx public key: 12eaf8f60315cb47d871dd0cf9fbd7aaac84621711c4247e4481d5d4bb83c7bc
Timestamp: 1713186587 Timestamp [UCT]: 2024-04-15 13:09:47 Age [y:d:h:m:s]: 00:223:00:31:44
Block: 1001065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159657 RingCT/type: yes/0
Extra: 0112eaf8f60315cb47d871dd0cf9fbd7aaac84621711c4247e4481d5d4bb83c7bc0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76ec446933dbea50793582c579c419b5fd69f020aece8a9298d256afff70de5a 0.600000000000 1461567 of 15

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": 1001075, "vin": [ { "gen": { "height": 1001065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76ec446933dbea50793582c579c419b5fd69f020aece8a9298d256afff70de5a" } } ], "extra": [ 1, 18, 234, 248, 246, 3, 21, 203, 71, 216, 113, 221, 12, 249, 251, 215, 170, 172, 132, 98, 23, 17, 196, 36, 126, 68, 129, 213, 212, 187, 131, 199, 188, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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