Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40010d428674979207170e85ee8ab3a7654efbc015b68dc987d8831746a22f71

Tx prefix hash: 8cb1dfc7a9f7a57027b5c4525fcc9b1346da80832aa9026005b9a7e849f724da
Tx public key: d5bbe8beaa5bd70e07e206e7c6f6a46a56aad430b1c7688745ceb8442b420f90
Timestamp: 1728420191 Timestamp [UCT]: 2024-10-08 20:43:11 Age [y:d:h:m:s]: 00:170:08:41:29
Block: 1127365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121539 RingCT/type: yes/0
Extra: 01d5bbe8beaa5bd70e07e206e7c6f6a46a56aad430b1c7688745ceb8442b420f9002110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9d384227e9e7794f32dde2e64ee27f5117fbe2411d7be3dd030ac0bacbbd4f0 0.600000000000 1610170 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": 1127375, "vin": [ { "gen": { "height": 1127365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9d384227e9e7794f32dde2e64ee27f5117fbe2411d7be3dd030ac0bacbbd4f0" } } ], "extra": [ 1, 213, 187, 232, 190, 170, 91, 215, 14, 7, 226, 6, 231, 198, 246, 164, 106, 86, 170, 212, 48, 177, 199, 104, 135, 69, 206, 184, 68, 43, 66, 15, 144, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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