Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce2968bd8a98ebf78784f4e6a905cc87d1d769f99180d1aadcb39a76c060fa9

Tx prefix hash: 492d1b6435ec9ec7e6ef963c526186114fcd89f8aff270515af008e4cfeeb0f2
Tx public key: d6306fa528dbd101d7b7488a7e8e46e479beb40d7a3bb5a0ac6cc62b0a5edd6d
Timestamp: 1625629131 Timestamp [UCT]: 2021-07-07 03:38:51 Age [y:d:h:m:s]: 03:217:12:28:38
Block: 289446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 925449 RingCT/type: yes/0
Extra: 01d6306fa528dbd101d7b7488a7e8e46e479beb40d7a3bb5a0ac6cc62b0a5edd6d021100000016d142c209000000000000000000

1 output(s) for total of 67.444377911000 dcy

stealth address amount amount idx
00: b7387ea35d50a831126b399f2035bac58b5ddef1c2c6a34d3264d7ef44c0bc2e 67.444377911000 606220 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": 289456, "vin": [ { "gen": { "height": 289446 } } ], "vout": [ { "amount": 67444377911, "target": { "key": "b7387ea35d50a831126b399f2035bac58b5ddef1c2c6a34d3264d7ef44c0bc2e" } } ], "extra": [ 1, 214, 48, 111, 165, 40, 219, 209, 1, 215, 183, 72, 138, 126, 142, 70, 228, 121, 190, 180, 13, 122, 59, 181, 160, 172, 108, 198, 43, 10, 94, 221, 109, 2, 17, 0, 0, 0, 22, 209, 66, 194, 9, 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