Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8e257e272e62eeed4754be1ea36b5136bc11c045839c37083da92c5fe2fc639

Tx prefix hash: a5e11b5b9c4e78a889508e39081f7149ac88ea28cfc20de047a973f9e5bd3a4d
Tx public key: 1bdfb193ffd3695525b3e59633235c94bc5d0e197005f20980ffe614c9a1bdc6
Timestamp: 1722004343 Timestamp [UCT]: 2024-07-26 14:32:23 Age [y:d:h:m:s]: 00:284:17:51:20
Block: 1074175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203427 RingCT/type: yes/0
Extra: 011bdfb193ffd3695525b3e59633235c94bc5d0e197005f20980ffe614c9a1bdc6021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3adab52838db94da0f31a65d2eaf9d26b3e1c83cff2b2a968e39cbbee09dddfc 0.600000000000 1546688 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": 1074185, "vin": [ { "gen": { "height": 1074175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3adab52838db94da0f31a65d2eaf9d26b3e1c83cff2b2a968e39cbbee09dddfc" } } ], "extra": [ 1, 27, 223, 177, 147, 255, 211, 105, 85, 37, 179, 229, 150, 51, 35, 92, 148, 188, 93, 14, 25, 112, 5, 242, 9, 128, 255, 230, 20, 201, 161, 189, 198, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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