Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf1ecd786247420f7b9ca4cbe8dd4a3da12c2ae44117685a806d8179b5c91aaa

Tx prefix hash: 73819420d0ed27f34ff23000d7a7c803db0f8d411a8eb3181d21d9ba3a6c33f1
Tx public key: e4ca297a38f6169c36377d701b1a0ce97918329956c0413d71fbc9ef1531253f
Timestamp: 1635027631 Timestamp [UCT]: 2021-10-23 22:20:31 Age [y:d:h:m:s]: 03:142:16:56:41
Block: 359105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 880099 RingCT/type: yes/0
Extra: 01e4ca297a38f6169c36377d701b1a0ce97918329956c0413d71fbc9ef1531253f0211000000024a0f5013000000000000000000

1 output(s) for total of 39.640258112000 dcy

stealth address amount amount idx
00: 74fe7e6c12cab7e061cc98304caddfff589f6e8536f55e29d66787cc4ab114ca 39.640258112000 731416 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": 359115, "vin": [ { "gen": { "height": 359105 } } ], "vout": [ { "amount": 39640258112, "target": { "key": "74fe7e6c12cab7e061cc98304caddfff589f6e8536f55e29d66787cc4ab114ca" } } ], "extra": [ 1, 228, 202, 41, 122, 56, 246, 22, 156, 54, 55, 125, 112, 27, 26, 12, 233, 121, 24, 50, 153, 86, 192, 65, 61, 113, 251, 201, 239, 21, 49, 37, 63, 2, 17, 0, 0, 0, 2, 74, 15, 80, 19, 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