Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b38a1a2b24a85791e4aa9d0535d1786febaad6b47589882866e18739de01cf2

Tx prefix hash: 3ef49fa62710e587103ad2db751fa3a3686fcaeeb225616acd9830763f42302a
Tx public key: bd7ccfc4932de3b8df93885f85f67e32926b2aa3a07ebba705c253958c2d577f
Timestamp: 1706573190 Timestamp [UCT]: 2024-01-30 00:06:30 Age [y:d:h:m:s]: 01:097:07:39:39
Block: 946221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330653 RingCT/type: yes/0
Extra: 01bd7ccfc4932de3b8df93885f85f67e32926b2aa3a07ebba705c253958c2d577f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f580b3c20dc018789ddd0b260d7223ebdb2e6299c7c9338b3e576f84018026e 0.600000000000 1404553 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": 946231, "vin": [ { "gen": { "height": 946221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f580b3c20dc018789ddd0b260d7223ebdb2e6299c7c9338b3e576f84018026e" } } ], "extra": [ 1, 189, 124, 207, 196, 147, 45, 227, 184, 223, 147, 136, 95, 133, 246, 126, 50, 146, 107, 42, 163, 160, 126, 187, 167, 5, 194, 83, 149, 140, 45, 87, 127, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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