Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc45b4231544c8f7e00c0c90c464625a70861baef3e097286e1c87efb52e9af5

Tx prefix hash: 6e5d4ffe6c6f4f7e6264997eb4f5064229a1a3cbafd03a60bd3cf26d98246459
Tx public key: 56ccb6e7bd438498eb6d64f092f3321d3fe244460fa31fdb4f258f6468ecb15f
Timestamp: 1721690166 Timestamp [UCT]: 2024-07-22 23:16:06 Age [y:d:h:m:s]: 00:297:11:24:03
Block: 1071554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212553 RingCT/type: yes/0
Extra: 0156ccb6e7bd438498eb6d64f092f3321d3fe244460fa31fdb4f258f6468ecb15f02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e72f0e74820048d49fb42258d3b1e95521fdb10759d54ccd2d0ccf52d8947246 0.600000000000 1543829 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": 1071564, "vin": [ { "gen": { "height": 1071554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e72f0e74820048d49fb42258d3b1e95521fdb10759d54ccd2d0ccf52d8947246" } } ], "extra": [ 1, 86, 204, 182, 231, 189, 67, 132, 152, 235, 109, 100, 240, 146, 243, 50, 29, 63, 226, 68, 70, 15, 163, 31, 219, 79, 37, 143, 100, 104, 236, 177, 95, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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