Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5838c9c15dc2e094cc0d05a541fd5ad2ff453db2484d6ebbc6cdd83f8adf5aa

Tx prefix hash: 9d5b618aaec9fa27f9168b89189a695161035116beb2a4a26103bac69ca0763e
Tx public key: ed39051956c71d2a9597a45abcfca18db07503b13d334540f6c4c0cb368e1a06
Timestamp: 1729755803 Timestamp [UCT]: 2024-10-24 07:43:23 Age [y:d:h:m:s]: 00:091:17:05:10
Block: 1138407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65529 RingCT/type: yes/0
Extra: 01ed39051956c71d2a9597a45abcfca18db07503b13d334540f6c4c0cb368e1a06021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a74330eb5973c7d9c6c7ce106153c52f2f299394ff2d7041a571ad756d9447f 0.600000000000 1622070 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": 1138417, "vin": [ { "gen": { "height": 1138407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a74330eb5973c7d9c6c7ce106153c52f2f299394ff2d7041a571ad756d9447f" } } ], "extra": [ 1, 237, 57, 5, 25, 86, 199, 29, 42, 149, 151, 164, 90, 188, 252, 161, 141, 176, 117, 3, 177, 61, 51, 69, 64, 246, 196, 192, 203, 54, 142, 26, 6, 2, 17, 0, 0, 0, 3, 0, 127, 151, 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