Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea94da3c00907e23e8bbe01eb4c986f3c1d241626f69ab1796868ce56ac6d3fa

Tx prefix hash: 5fded3df2aac93b965925f6246eea1436e76db27841ef346d8b7473e6a97e155
Tx public key: 843255c4ccb2fbd94a418e1559e156a9e7b4d1f2851b575a9fe17de711c9ac65
Timestamp: 1711160156 Timestamp [UCT]: 2024-03-23 02:15:56 Age [y:d:h:m:s]: 01:225:23:03:14
Block: 984287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420167 RingCT/type: yes/0
Extra: 01843255c4ccb2fbd94a418e1559e156a9e7b4d1f2851b575a9fe17de711c9ac650211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0cc286d3f557591d408e3803162e0d34983a1608d4bea09d7d9a91055542b3b 0.600000000000 1444456 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": 984297, "vin": [ { "gen": { "height": 984287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0cc286d3f557591d408e3803162e0d34983a1608d4bea09d7d9a91055542b3b" } } ], "extra": [ 1, 132, 50, 85, 196, 204, 178, 251, 217, 74, 65, 142, 21, 89, 225, 86, 169, 231, 180, 209, 242, 133, 27, 87, 90, 159, 225, 125, 231, 17, 201, 172, 101, 2, 17, 0, 0, 0, 9, 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