Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5e1ee792e8081c0b70726be37819ad5c51a66216d4110e70fbc30ba605a3012

Tx prefix hash: a4bf8a85bc63892238c388a0c8a84ab2344b2755bf8ce530eb98d88420a2a721
Tx public key: a40974d2d2d43a5df1b9ce4dc37ff3b9ec11cc55275ead2782e9fdc2a6a2bb6c
Timestamp: 1645483673 Timestamp [UCT]: 2022-02-21 22:47:53 Age [y:d:h:m:s]: 03:064:23:19:09
Block: 443642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 826509 RingCT/type: yes/0
Extra: 01a40974d2d2d43a5df1b9ce4dc37ff3b9ec11cc55275ead2782e9fdc2a6a2bb6c0211000000054da16a3a000000000000000000

1 output(s) for total of 20.798412026000 dcy

stealth address amount amount idx
00: b985d2d7cb242968022cb7a329a53728050cfd2e291be998fd701b4cc9b52f15 20.798412026000 856731 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": 443652, "vin": [ { "gen": { "height": 443642 } } ], "vout": [ { "amount": 20798412026, "target": { "key": "b985d2d7cb242968022cb7a329a53728050cfd2e291be998fd701b4cc9b52f15" } } ], "extra": [ 1, 164, 9, 116, 210, 210, 212, 58, 93, 241, 185, 206, 77, 195, 127, 243, 185, 236, 17, 204, 85, 39, 94, 173, 39, 130, 233, 253, 194, 166, 162, 187, 108, 2, 17, 0, 0, 0, 5, 77, 161, 106, 58, 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