Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e100fe20169382c017cdac2e486f63d12ea7552d6a0300286d2399f600b8a91c

Tx prefix hash: 65f17ae1c4f415fc18e071c51c1c821698b0949cbec76cd093a6b9befcb7eb1f
Tx public key: fb903f400fc91f3b217f5735b48813225e77f5545da64b4fded6cebdf3e3a124
Timestamp: 1626821814 Timestamp [UCT]: 2021-07-20 22:56:54 Age [y:d:h:m:s]: 03:169:01:07:23
Block: 297849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 892525 RingCT/type: yes/0
Extra: 01fb903f400fc91f3b217f5735b48813225e77f5545da64b4fded6cebdf3e3a12402110000001204712537000000000000000000

1 output(s) for total of 63.256202144000 dcy

stealth address amount amount idx
00: ea1c44ab3132f7f85d8e9c368c0472d483df827f6b6b61198718d29f6a2006d5 63.256202144000 623344 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": 297859, "vin": [ { "gen": { "height": 297849 } } ], "vout": [ { "amount": 63256202144, "target": { "key": "ea1c44ab3132f7f85d8e9c368c0472d483df827f6b6b61198718d29f6a2006d5" } } ], "extra": [ 1, 251, 144, 63, 64, 15, 201, 31, 59, 33, 127, 87, 53, 180, 136, 19, 34, 94, 119, 245, 84, 93, 166, 75, 79, 222, 214, 206, 189, 243, 227, 161, 36, 2, 17, 0, 0, 0, 18, 4, 113, 37, 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