Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5277524c7ffb1f843bca1126574c2f74001a0eb2a747d5bc6fff2c833e71a99f

Tx prefix hash: f953526523126c71a7b8bddb409c5acc5d77158a982319a4c631dfe4af182e1e
Tx public key: e53ea8cc3bec9feb0e19efc2487876cf3e53c690d0648e123e6145e31a80007a
Timestamp: 1648670466 Timestamp [UCT]: 2022-03-30 20:01:06 Age [y:d:h:m:s]: 03:216:00:49:44
Block: 469789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 932388 RingCT/type: yes/0
Extra: 01e53ea8cc3bec9feb0e19efc2487876cf3e53c690d0648e123e6145e31a80007a021100000001c9067537000000000000000000

1 output(s) for total of 17.037045140000 dcy

stealth address amount amount idx
00: 1c78854d97e2e34dc302311e1feabda5b81673545af366d8c457fb04ed03f2ad 17.037045140000 888803 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": 469799, "vin": [ { "gen": { "height": 469789 } } ], "vout": [ { "amount": 17037045140, "target": { "key": "1c78854d97e2e34dc302311e1feabda5b81673545af366d8c457fb04ed03f2ad" } } ], "extra": [ 1, 229, 62, 168, 204, 59, 236, 159, 235, 14, 25, 239, 194, 72, 120, 118, 207, 62, 83, 198, 144, 208, 100, 142, 18, 62, 97, 69, 227, 26, 128, 0, 122, 2, 17, 0, 0, 0, 1, 201, 6, 117, 55, 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