Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f50de8006683a0ee13c4fffd3e9577de7d93965d2e29eab33ca5044cf9101f12

Tx prefix hash: cdfa3b006783954703926b57f107b017e5cc381efcd407b71bf68d3c97c1c65b
Tx public key: 69e6cc534adfe041ccace01f6836be66aad8cc4df595b355c0f8a79c1035ff6e
Timestamp: 1626838300 Timestamp [UCT]: 2021-07-21 03:31:40 Age [y:d:h:m:s]: 03:220:00:49:35
Block: 297967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 928719 RingCT/type: yes/0
Extra: 0169e6cc534adfe041ccace01f6836be66aad8cc4df595b355c0f8a79c1035ff6e02110000000437cb3088000000000000000000

1 output(s) for total of 63.199279984000 dcy

stealth address amount amount idx
00: 35ff83d7dc57e4be8bf1dc19aab20857b051a968c6548168c9c2b66ee47d1b15 63.199279984000 623568 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": 297977, "vin": [ { "gen": { "height": 297967 } } ], "vout": [ { "amount": 63199279984, "target": { "key": "35ff83d7dc57e4be8bf1dc19aab20857b051a968c6548168c9c2b66ee47d1b15" } } ], "extra": [ 1, 105, 230, 204, 83, 74, 223, 224, 65, 204, 172, 224, 31, 104, 54, 190, 102, 170, 216, 204, 77, 245, 149, 179, 85, 192, 248, 167, 156, 16, 53, 255, 110, 2, 17, 0, 0, 0, 4, 55, 203, 48, 136, 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