Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bfcaefbd44f5f2d7bfea41e108f7100639d2e0c16f818cbb889e8fd797bbbc5

Tx prefix hash: bc40f2cdb32db837a6dc781dbf3ed742c0d7599ed1fc3a773c3e4e1cd48d2f9c
Tx public key: 9370fc1ece445d04fb15433c70ac11b8a9595b97f4ff18343c88b90b3795dd0d
Timestamp: 1663803968 Timestamp [UCT]: 2022-09-21 23:46:08 Age [y:d:h:m:s]: 03:040:23:11:07
Block: 592989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 809254 RingCT/type: yes/0
Extra: 019370fc1ece445d04fb15433c70ac11b8a9595b97f4ff18343c88b90b3795dd0d021100000001798ce684000000000000000000

1 output(s) for total of 6.655510173000 dcy

stealth address amount amount idx
00: a0b7c800510a0c80ae54524741eac4c4e1f726adf939b9814b9e4c903d70667d 6.655510173000 1027702 of 0

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": 592999, "vin": [ { "gen": { "height": 592989 } } ], "vout": [ { "amount": 6655510173, "target": { "key": "a0b7c800510a0c80ae54524741eac4c4e1f726adf939b9814b9e4c903d70667d" } } ], "extra": [ 1, 147, 112, 252, 30, 206, 68, 93, 4, 251, 21, 67, 60, 112, 172, 17, 184, 169, 89, 91, 151, 244, 255, 24, 52, 60, 136, 185, 11, 55, 149, 221, 13, 2, 17, 0, 0, 0, 1, 121, 140, 230, 132, 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