Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6771c1f02bb7df1844ef09d6a09d8cef6ec7baa21468f6e0927ce079dcd7576f

Tx prefix hash: 59e094766327ec2532eff2d5873c70290263c766f7302b442e58af45ee977f57
Tx public key: c71b589faf068438236e7584a6ff2b054c57aca0b67f75eb39bdcfd1a0aaab3f
Timestamp: 1748704312 Timestamp [UCT]: 2025-05-31 15:11:52 Age [y:d:h:m:s]: 00:170:23:33:48
Block: 1295001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119872 RingCT/type: yes/0
Extra: 01c71b589faf068438236e7584a6ff2b054c57aca0b67f75eb39bdcfd1a0aaab3f02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 044bdfa2192a4bfc9f4fbf4d15ae1dc786b0d5f877962a479f49c7812a9a9e36 0.600000000000 1782498 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": 1295011, "vin": [ { "gen": { "height": 1295001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "044bdfa2192a4bfc9f4fbf4d15ae1dc786b0d5f877962a479f49c7812a9a9e36" } } ], "extra": [ 1, 199, 27, 88, 159, 175, 6, 132, 56, 35, 110, 117, 132, 166, 255, 43, 5, 76, 87, 172, 160, 182, 127, 117, 235, 57, 189, 207, 209, 160, 170, 171, 63, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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