Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1e2beef4854a7d7479f15b497f07ed84b3d6a64bfbf4174a60fc626d667f376

Tx prefix hash: 45d006f3f286876a4df4d3aac83539f67f2af570ca891793762528412b84a33d
Tx public key: 553bad2bd3f617ce65cd4f9a0b58a467bcdfa7e45d23141685982dec0f3849f2
Timestamp: 1728738683 Timestamp [UCT]: 2024-10-12 13:11:23 Age [y:d:h:m:s]: 00:176:10:20:46
Block: 1130007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125861 RingCT/type: yes/0
Extra: 01553bad2bd3f617ce65cd4f9a0b58a467bcdfa7e45d23141685982dec0f3849f202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 106f11ddb446e7265b31d34f51323b6d1042d98f7eaefdbb7d493d4a997e851a 0.600000000000 1612878 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": 1130017, "vin": [ { "gen": { "height": 1130007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "106f11ddb446e7265b31d34f51323b6d1042d98f7eaefdbb7d493d4a997e851a" } } ], "extra": [ 1, 85, 59, 173, 43, 211, 246, 23, 206, 101, 205, 79, 154, 11, 88, 164, 103, 188, 223, 167, 228, 93, 35, 20, 22, 133, 152, 45, 236, 15, 56, 73, 242, 2, 17, 0, 0, 0, 2, 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