Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c26821378e475b571afc492eaaaddfc212390809ba2d67b8ad71c46fb9a9ec8

Tx prefix hash: cf57915b18bc7f32337b0ca11eedfa7d12b6a6655d3a5a6d8b6fbfe877a33637
Tx public key: 3c75ab3736bf69f7aca7dc0f724bc96d409d554aef2323694f4453aec40b55c2
Timestamp: 1634694493 Timestamp [UCT]: 2021-10-20 01:48:13 Age [y:d:h:m:s]: 03:030:16:37:10
Block: 356550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 800009 RingCT/type: yes/0
Extra: 013c75ab3736bf69f7aca7dc0f724bc96d409d554aef2323694f4453aec40b55c20211000000138d0de867000000000000000000

1 output(s) for total of 40.420553203000 dcy

stealth address amount amount idx
00: b457f03191b51b385fef8ce55b883590e8af5dd4a0818f86ff85b96fc1580e6a 40.420553203000 727426 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": 356560, "vin": [ { "gen": { "height": 356550 } } ], "vout": [ { "amount": 40420553203, "target": { "key": "b457f03191b51b385fef8ce55b883590e8af5dd4a0818f86ff85b96fc1580e6a" } } ], "extra": [ 1, 60, 117, 171, 55, 54, 191, 105, 247, 172, 167, 220, 15, 114, 75, 201, 109, 64, 157, 85, 74, 239, 35, 35, 105, 79, 68, 83, 174, 196, 11, 85, 194, 2, 17, 0, 0, 0, 19, 141, 13, 232, 103, 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