Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8fa927d02f2547f2b611e2a2918d878b43bf2ff61c119a4b44c4f937a562c81

Tx prefix hash: 52edc12d4f8b96f594aa7dbb1b3dfb409b43c23e89172be57adb6ce49a2d4d68
Tx public key: 664a9a01e4a56191015722c61ecda30ede1819354a19a6c83cabf2c8d0f33f4a
Timestamp: 1673209414 Timestamp [UCT]: 2023-01-08 20:23:34 Age [y:d:h:m:s]: 02:304:10:10:48
Block: 670490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 736979 RingCT/type: yes/0
Extra: 01664a9a01e4a56191015722c61ecda30ede1819354a19a6c83cabf2c8d0f33f4a02110000000252542ceb000000000000000000

1 output(s) for total of 3.684582227000 dcy

stealth address amount amount idx
00: 2c04bfad1e3fc7d96c1be4e25082fcaf95dffc1d35b484d2cc3c336b413717b5 3.684582227000 1111899 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": 670500, "vin": [ { "gen": { "height": 670490 } } ], "vout": [ { "amount": 3684582227, "target": { "key": "2c04bfad1e3fc7d96c1be4e25082fcaf95dffc1d35b484d2cc3c336b413717b5" } } ], "extra": [ 1, 102, 74, 154, 1, 228, 165, 97, 145, 1, 87, 34, 198, 30, 205, 163, 14, 222, 24, 25, 53, 74, 25, 166, 200, 60, 171, 242, 200, 208, 243, 63, 74, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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