Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c680840fabc71a8c8044f47f311a3edcfa90c2e3d0812941b4b42344c0e8ce7

Tx prefix hash: 45138b7453c454139528e281b9db61141671ff00fddadc020d219d3ecd139c6a
Tx public key: 672373092a7175556e41d4421f02ea2cfe77b524f8afb9b23b34698bed8af825
Timestamp: 1676492915 Timestamp [UCT]: 2023-02-15 20:28:35 Age [y:d:h:m:s]: 01:348:03:22:48
Block: 697742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509524 RingCT/type: yes/0
Extra: 01672373092a7175556e41d4421f02ea2cfe77b524f8afb9b23b34698bed8af82502110000000374b6d784000000000000000000

1 output(s) for total of 2.992891853000 dcy

stealth address amount amount idx
00: a76a5f82d08ae7bf6befeca8bee0f63bb3a6d022be701a39a363e9cb88bd405e 2.992891853000 1140991 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": 697752, "vin": [ { "gen": { "height": 697742 } } ], "vout": [ { "amount": 2992891853, "target": { "key": "a76a5f82d08ae7bf6befeca8bee0f63bb3a6d022be701a39a363e9cb88bd405e" } } ], "extra": [ 1, 103, 35, 115, 9, 42, 113, 117, 85, 110, 65, 212, 66, 31, 2, 234, 44, 254, 119, 181, 36, 248, 175, 185, 178, 59, 52, 105, 139, 237, 138, 248, 37, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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