Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04dc9d3c4ed60fc5225acb490a4c5a92c6a6dbeda1355e30a88a6ece158ca737

Tx prefix hash: 2da9685782ef092315feea7333c1805825e17b1e42fe88eb463b35acd21df1ef
Tx public key: 1fe5e9285ab6b8f9a50e2dc9894a3d5bfcff59ad9f368e37bb3f127d1419a733
Timestamp: 1582396315 Timestamp [UCT]: 2020-02-22 18:31:55 Age [y:d:h:m:s]: 05:097:03:17:42
Block: 70400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1222638 RingCT/type: yes/0
Extra: 011fe5e9285ab6b8f9a50e2dc9894a3d5bfcff59ad9f368e37bb3f127d1419a7330211000000244ac5aa02000000000000000000

1 output(s) for total of 358.704131352000 dcy

stealth address amount amount idx
00: f4cb025a4d4c2ab6f69bc670fe2a0f98da908a3a3ae7664c891e81b44918d15e 358.704131352000 130053 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": 70410, "vin": [ { "gen": { "height": 70400 } } ], "vout": [ { "amount": 358704131352, "target": { "key": "f4cb025a4d4c2ab6f69bc670fe2a0f98da908a3a3ae7664c891e81b44918d15e" } } ], "extra": [ 1, 31, 229, 233, 40, 90, 182, 184, 249, 165, 14, 45, 201, 137, 74, 61, 91, 252, 255, 89, 173, 159, 54, 142, 55, 187, 63, 18, 125, 20, 25, 167, 51, 2, 17, 0, 0, 0, 36, 74, 197, 170, 2, 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