Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b85ad0dc8ff1d5ee64866620af2138345d2c473b403d9cabf517e4f8b191a6f4

Tx prefix hash: dd9f2eb2db3b594f113a0b45d2fba237198539aaa63861c98b487c0893f029a5
Tx public key: 739b3b82e2f80a1531f8ae578c74ea2ec21519268bb327142aa4cb9c9b180533
Timestamp: 1630620532 Timestamp [UCT]: 2021-09-02 22:08:52 Age [y:d:h:m:s]: 03:164:18:05:45
Block: 326205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 892272 RingCT/type: yes/0
Extra: 01739b3b82e2f80a1531f8ae578c74ea2ec21519268bb327142aa4cb9c9b18053302110000001a0441b428000000000000000000

1 output(s) for total of 50.950432269000 dcy

stealth address amount amount idx
00: 60fa79b8aafbdc9e6b2cd85523e861135b400e0916d2f2a9db59c6ee0eed5e95 50.950432269000 675942 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": 326215, "vin": [ { "gen": { "height": 326205 } } ], "vout": [ { "amount": 50950432269, "target": { "key": "60fa79b8aafbdc9e6b2cd85523e861135b400e0916d2f2a9db59c6ee0eed5e95" } } ], "extra": [ 1, 115, 155, 59, 130, 226, 248, 10, 21, 49, 248, 174, 87, 140, 116, 234, 46, 194, 21, 25, 38, 139, 179, 39, 20, 42, 164, 203, 156, 155, 24, 5, 51, 2, 17, 0, 0, 0, 26, 4, 65, 180, 40, 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