Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9005b381837302c5c585bd4e789353b09bbc54257358958aef9d62c179f8a6a

Tx prefix hash: 723dd19e0945679015977a1737711c082272dc528683a56228be89c65dd1eaa0
Tx public key: 64f0fb16833485234c56c65ec4f5a59d7bde8f30b57a5c00230035e91eeb303d
Timestamp: 1581240800 Timestamp [UCT]: 2020-02-09 09:33:20 Age [y:d:h:m:s]: 04:359:03:13:52
Block: 61170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148617 RingCT/type: yes/0
Extra: 0164f0fb16833485234c56c65ec4f5a59d7bde8f30b57a5c00230035e91eeb303d0211000000024943cd9f000000000000000000

1 output(s) for total of 384.874567381000 dcy

stealth address amount amount idx
00: 263098323306e3f81683fb67b3d9d91caf04d54e8fbf6d5ce0d5764a5845477c 384.874567381000 112729 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": 61180, "vin": [ { "gen": { "height": 61170 } } ], "vout": [ { "amount": 384874567381, "target": { "key": "263098323306e3f81683fb67b3d9d91caf04d54e8fbf6d5ce0d5764a5845477c" } } ], "extra": [ 1, 100, 240, 251, 22, 131, 52, 133, 35, 76, 86, 198, 94, 196, 245, 165, 157, 123, 222, 143, 48, 181, 122, 92, 0, 35, 0, 53, 233, 30, 235, 48, 61, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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