Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa65dfd5c0405cf7151c46d77a0d43ef4d2c8936f367a849a40507639a2b7c38

Tx prefix hash: b4c181effcca8aac392fb067e220e0730bddeb02fa19282c8650bfe1575478c8
Tx public key: 51e5f5af07d6ac812d26a5693c32ceda8e494180555506c23fa4d4a8fa05b3e4
Timestamp: 1723303679 Timestamp [UCT]: 2024-08-10 15:27:59 Age [y:d:h:m:s]: 00:222:06:08:55
Block: 1084946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158741 RingCT/type: yes/0
Extra: 0151e5f5af07d6ac812d26a5693c32ceda8e494180555506c23fa4d4a8fa05b3e402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 837411c52a4dc237166d3b13a88bf08e6bfff08b5eea21e1f008cbe9a997e069 0.600000000000 1559405 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": 1084956, "vin": [ { "gen": { "height": 1084946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "837411c52a4dc237166d3b13a88bf08e6bfff08b5eea21e1f008cbe9a997e069" } } ], "extra": [ 1, 81, 229, 245, 175, 7, 214, 172, 129, 45, 38, 165, 105, 60, 50, 206, 218, 142, 73, 65, 128, 85, 85, 6, 194, 63, 164, 212, 168, 250, 5, 179, 228, 2, 17, 0, 0, 0, 7, 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