Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7910631251b7d4efe6091b513f69223c427f069867a93b2d492fee624f9c0893

Tx prefix hash: 467dbe594852bd597c4a47c1e116e6de194a679d037a80447370e9dae08deccd
Tx public key: b03dad2f59dfd0a586cc4d8e59da3e7a3f983d5bae85b5b4b41b93818f11f7bf
Timestamp: 1637506978 Timestamp [UCT]: 2021-11-21 15:02:58 Age [y:d:h:m:s]: 03:207:16:48:31
Block: 379050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 927052 RingCT/type: yes/0
Extra: 01b03dad2f59dfd0a586cc4d8e59da3e7a3f983d5bae85b5b4b41b93818f11f7bf0211000000011cab2639000000000000000000

1 output(s) for total of 34.044768155000 dcy

stealth address amount amount idx
00: 383790b81021d58499f0f1fe29a022853846ad1e278902f5e7fe1f90ffea5c73 34.044768155000 766324 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": 379060, "vin": [ { "gen": { "height": 379050 } } ], "vout": [ { "amount": 34044768155, "target": { "key": "383790b81021d58499f0f1fe29a022853846ad1e278902f5e7fe1f90ffea5c73" } } ], "extra": [ 1, 176, 61, 173, 47, 89, 223, 208, 165, 134, 204, 77, 142, 89, 218, 62, 122, 63, 152, 61, 91, 174, 133, 181, 180, 180, 27, 147, 129, 143, 17, 247, 191, 2, 17, 0, 0, 0, 1, 28, 171, 38, 57, 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