Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dd7b1ab653125fa7c2114d456986c900dd74ebd5eabb87c59a565898d0ccba5

Tx prefix hash: 1ed5a695456df2b7a669f6d2856b415be476b0cd5f3d8c050d1701f73cc6366b
Tx public key: 74fb01af16f2fd77be580a3718ac7bffb02189ca4e3e7f8cd5b78d9c8190e3ac
Timestamp: 1728428726 Timestamp [UCT]: 2024-10-08 23:05:26 Age [y:d:h:m:s]: 00:252:13:26:28
Block: 1127429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180228 RingCT/type: yes/0
Extra: 0174fb01af16f2fd77be580a3718ac7bffb02189ca4e3e7f8cd5b78d9c8190e3ac021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 194d8a33ffc233d9ee260555f1bfa45a447335ad05f4e74edd5493a18d244cfb 0.600000000000 1610234 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": 1127439, "vin": [ { "gen": { "height": 1127429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "194d8a33ffc233d9ee260555f1bfa45a447335ad05f4e74edd5493a18d244cfb" } } ], "extra": [ 1, 116, 251, 1, 175, 22, 242, 253, 119, 190, 88, 10, 55, 24, 172, 123, 255, 176, 33, 137, 202, 78, 62, 127, 140, 213, 183, 141, 156, 129, 144, 227, 172, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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