Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8691c71c19e57576a4b1238f56c0b66b9f1bebaac1e8741f9e79cf3ee1997b8

Tx prefix hash: 280269db352ddcbbae785f54ebe6564fa1e4f80288e618b9df888f21a069c37d
Tx public key: 8f9f710779bdb5dd6d66cf2b832ecfa34f811741e004d700b0c5e6433188589a
Timestamp: 1659365718 Timestamp [UCT]: 2022-08-01 14:55:18 Age [y:d:h:m:s]: 02:195:19:59:41
Block: 556464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 661144 RingCT/type: yes/0
Extra: 018f9f710779bdb5dd6d66cf2b832ecfa34f811741e004d700b0c5e6433188589a02110000000fd834ebe0000000000000000000

1 output(s) for total of 8.794352953000 dcy

stealth address amount amount idx
00: f8f3310230e55ccf9e81d08942eb195f3306fbeb51b3072e3a7cfc73764b8ba7 8.794352953000 988404 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": 556474, "vin": [ { "gen": { "height": 556464 } } ], "vout": [ { "amount": 8794352953, "target": { "key": "f8f3310230e55ccf9e81d08942eb195f3306fbeb51b3072e3a7cfc73764b8ba7" } } ], "extra": [ 1, 143, 159, 113, 7, 121, 189, 181, 221, 109, 102, 207, 43, 131, 46, 207, 163, 79, 129, 23, 65, 224, 4, 215, 0, 176, 197, 230, 67, 49, 136, 88, 154, 2, 17, 0, 0, 0, 15, 216, 52, 235, 224, 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