Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c76e46f23f57c878c25342267bab83493b6f4cb6b672361a431b5966c024ced4

Tx prefix hash: 3145880699a07e9b09feec30e2cc66bf332ff2ebdd62a77673fe52f434e14d6e
Tx public key: cf0d1b0ce86e74be9ad718f08cb36d2a52ede7916724f1b072cca1678bd16cae
Timestamp: 1580016663 Timestamp [UCT]: 2020-01-26 05:31:03 Age [y:d:h:m:s]: 05:038:22:44:20
Block: 53237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178465 RingCT/type: yes/0
Extra: 01cf0d1b0ce86e74be9ad718f08cb36d2a52ede7916724f1b072cca1678bd16cae021100000002b221b3d1000000000000000000

1 output(s) for total of 408.888171725000 dcy

stealth address amount amount idx
00: bbe83f20442ce02d88602e3317a1b59777cb4b5b5e4e0e4e509c68c8ec559475 408.888171725000 98653 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": 53247, "vin": [ { "gen": { "height": 53237 } } ], "vout": [ { "amount": 408888171725, "target": { "key": "bbe83f20442ce02d88602e3317a1b59777cb4b5b5e4e0e4e509c68c8ec559475" } } ], "extra": [ 1, 207, 13, 27, 12, 232, 110, 116, 190, 154, 215, 24, 240, 140, 179, 109, 42, 82, 237, 231, 145, 103, 36, 241, 176, 114, 204, 161, 103, 139, 209, 108, 174, 2, 17, 0, 0, 0, 2, 178, 33, 179, 209, 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