Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5940a09b139ddcfe1fef6ff1ba894a2920c793967523a249812eb92ec06f713a

Tx prefix hash: 9ee5396b7b963a4a9f95f4e14d78bf9739c7e47f911f5daa38acef55adb8c94d
Tx public key: 25cdeaea5a80846647e86a74ddb6b557425dc2ea01019198f11257d9fe41cf0d
Timestamp: 1711861662 Timestamp [UCT]: 2024-03-31 05:07:42 Age [y:d:h:m:s]: 01:035:07:11:24
Block: 990098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286197 RingCT/type: yes/0
Extra: 0125cdeaea5a80846647e86a74ddb6b557425dc2ea01019198f11257d9fe41cf0d02110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e789caa19dc79d1e2b7e913767149ec7fc498afd0fead411ba0322aa99bde05c 0.600000000000 1450420 of 15

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": 990108, "vin": [ { "gen": { "height": 990098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e789caa19dc79d1e2b7e913767149ec7fc498afd0fead411ba0322aa99bde05c" } } ], "extra": [ 1, 37, 205, 234, 234, 90, 128, 132, 102, 71, 232, 106, 116, 221, 182, 181, 87, 66, 93, 194, 234, 1, 1, 145, 152, 241, 18, 87, 217, 254, 65, 207, 13, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 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