Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cf0d48139ad9033cdae4da3fffc551c05193fcc4fa7b260b6b81903b31a62b9

Tx prefix hash: 035a968d3d544c6e91dfc458ec7059f1eab69668e02c96c966da2b7c8819f25c
Tx public key: 3c522e546b5fcaf1ae185d7170dd597af4acb7e31ceeb2cde8b983d388cc44f9
Timestamp: 1711384188 Timestamp [UCT]: 2024-03-25 16:29:48 Age [y:d:h:m:s]: 01:073:15:56:06
Block: 986150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313641 RingCT/type: yes/0
Extra: 013c522e546b5fcaf1ae185d7170dd597af4acb7e31ceeb2cde8b983d388cc44f902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fded1de515373c826e5e11058af84aa8c14a7af44983fdf0943bcdb19da7c167 0.600000000000 1446377 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": 986160, "vin": [ { "gen": { "height": 986150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fded1de515373c826e5e11058af84aa8c14a7af44983fdf0943bcdb19da7c167" } } ], "extra": [ 1, 60, 82, 46, 84, 107, 95, 202, 241, 174, 24, 93, 113, 112, 221, 89, 122, 244, 172, 183, 227, 28, 238, 178, 205, 232, 185, 131, 211, 136, 204, 68, 249, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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