Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69c30ccbce7b9ee278466c793754cf8105f155c00ed018a05f98cdda64ba4157

Tx prefix hash: cd7f5f15e654036525ae8f08dd695085d04949dbc123d2c5b38efbb203fa897a
Tx public key: 79abd91fb811132d176c4a810b352f1a5c4c64aa0696a15ddf92ed22226e01f7
Timestamp: 1711709371 Timestamp [UCT]: 2024-03-29 10:49:31 Age [y:d:h:m:s]: 01:225:08:51:22
Block: 988842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419741 RingCT/type: yes/0
Extra: 0179abd91fb811132d176c4a810b352f1a5c4c64aa0696a15ddf92ed22226e01f702110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b01b81b364985c3c1bd3c2c4dfea37df99ce3253e85a5f4bbd035fc80d47166 0.600000000000 1449129 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": 988852, "vin": [ { "gen": { "height": 988842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b01b81b364985c3c1bd3c2c4dfea37df99ce3253e85a5f4bbd035fc80d47166" } } ], "extra": [ 1, 121, 171, 217, 31, 184, 17, 19, 45, 23, 108, 74, 129, 11, 53, 47, 26, 92, 76, 100, 170, 6, 150, 161, 93, 223, 146, 237, 34, 34, 110, 1, 247, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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