Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8e4645b9a2d8d372ffdd622ee0609482d315bf9ee421322b7dc5ac7d8df4438

Tx prefix hash: 833e0b7794530a450d56fef585c8b213bc388ce976f9018ed14ed597ca2930d4
Tx public key: 30b58897e10a3eb2188044f723984efdf83c604f3fce6f2efc5f54d5823169e3
Timestamp: 1593018113 Timestamp [UCT]: 2020-06-24 17:01:53 Age [y:d:h:m:s]: 04:341:10:05:05
Block: 110527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184099 RingCT/type: yes/0
Extra: 0130b58897e10a3eb2188044f723984efdf83c604f3fce6f2efc5f54d5823169e302110000001946a11e8a000000000000000000

1 output(s) for total of 264.106393241000 dcy

stealth address amount amount idx
00: 437686c1498ecfeab5d6c38e0c2910de8b72da5533dd00a792be3941ab8f0c60 264.106393241000 191413 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": 110537, "vin": [ { "gen": { "height": 110527 } } ], "vout": [ { "amount": 264106393241, "target": { "key": "437686c1498ecfeab5d6c38e0c2910de8b72da5533dd00a792be3941ab8f0c60" } } ], "extra": [ 1, 48, 181, 136, 151, 225, 10, 62, 178, 24, 128, 68, 247, 35, 152, 78, 253, 248, 60, 96, 79, 63, 206, 111, 46, 252, 95, 84, 213, 130, 49, 105, 227, 2, 17, 0, 0, 0, 25, 70, 161, 30, 138, 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