Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c481d96c6edb1860d3bf905348d064b8e7d131a9eed0002e4e97846bc2b7784c

Tx prefix hash: 60c874b02fb178b05e4d5151fc247c102c045a492a64f3106736713ff2ecb8b0
Tx public key: f7b7cc12eb84e6d51b76bf63bc212f4130d021fd39478034022633fb26b903b4
Timestamp: 1715632877 Timestamp [UCT]: 2024-05-13 20:41:17 Age [y:d:h:m:s]: 00:343:18:49:30
Block: 1021345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245743 RingCT/type: yes/0
Extra: 01f7b7cc12eb84e6d51b76bf63bc212f4130d021fd39478034022633fb26b903b40211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 756a5dd4674b840fa07b4ae72ac6d4c5fbf68c56ffd14d72dd982d7bd55934fb 0.600000000000 1485642 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": 1021355, "vin": [ { "gen": { "height": 1021345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "756a5dd4674b840fa07b4ae72ac6d4c5fbf68c56ffd14d72dd982d7bd55934fb" } } ], "extra": [ 1, 247, 183, 204, 18, 235, 132, 230, 213, 27, 118, 191, 99, 188, 33, 47, 65, 48, 208, 33, 253, 57, 71, 128, 52, 2, 38, 51, 251, 38, 185, 3, 180, 2, 17, 0, 0, 0, 1, 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