Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcc6d6aecfd7174b30d9d069e806aa8f4556f303cc8c019c29bc52fe4563a850

Tx prefix hash: 3263e97bb942599ca6597504f8aeaf3e867b74658855a31d91b280db08289b67
Tx public key: 4e7727c591e8a67652c536ad46d4dccfa4222016e2f70b3b1d8b606096eb8f3d
Timestamp: 1677819796 Timestamp [UCT]: 2023-03-03 05:03:16 Age [y:d:h:m:s]: 01:359:04:25:22
Block: 708750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517376 RingCT/type: yes/0
Extra: 014e7727c591e8a67652c536ad46d4dccfa4222016e2f70b3b1d8b606096eb8f3d0211000000035029cbac000000000000000000

1 output(s) for total of 2.751800431000 dcy

stealth address amount amount idx
00: 851901a6f90c28cdd6a3dd21ef9447250f643629067d4849f57778e0b2c5620f 2.751800431000 1152665 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": 708760, "vin": [ { "gen": { "height": 708750 } } ], "vout": [ { "amount": 2751800431, "target": { "key": "851901a6f90c28cdd6a3dd21ef9447250f643629067d4849f57778e0b2c5620f" } } ], "extra": [ 1, 78, 119, 39, 197, 145, 232, 166, 118, 82, 197, 54, 173, 70, 212, 220, 207, 164, 34, 32, 22, 226, 247, 11, 59, 29, 139, 96, 96, 150, 235, 143, 61, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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