Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 229d7e98385d326db3015a4122e13e2ee9aa7a55954717f1c8e00fcc20c3b688

Tx prefix hash: 4367100fb8c19a1dc14f4eb1e7a2b83d51d0198dd7046155868ff113a22ad85c
Tx public key: a58af5424e8be791ca5d5c3242999f8f685300068f5910c55d454c4e6966a09f
Timestamp: 1574305707 Timestamp [UCT]: 2019-11-21 03:08:27 Age [y:d:h:m:s]: 05:039:21:59:52
Block: 13483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1171897 RingCT/type: yes/0
Extra: 01a58af5424e8be791ca5d5c3242999f8f685300068f5910c55d454c4e6966a09f0211000000018ec07589000000000000000000

1 output(s) for total of 553.777764060000 dcy

stealth address amount amount idx
00: 8f8e52ee1e921af6d8e13fcc2bf719db4fa24af7a620ad05efb55265bd18b1f2 553.777764060000 16003 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": 13493, "vin": [ { "gen": { "height": 13483 } } ], "vout": [ { "amount": 553777764060, "target": { "key": "8f8e52ee1e921af6d8e13fcc2bf719db4fa24af7a620ad05efb55265bd18b1f2" } } ], "extra": [ 1, 165, 138, 245, 66, 78, 139, 231, 145, 202, 93, 92, 50, 66, 153, 159, 143, 104, 83, 0, 6, 143, 89, 16, 197, 93, 69, 76, 78, 105, 102, 160, 159, 2, 17, 0, 0, 0, 1, 142, 192, 117, 137, 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