Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0dcbe6a3203e755abed4eefef8c1a03b2deec4703a5caa88aac40210711532c

Tx prefix hash: 37a402e77076510da36bf0444dad78ae5a4aa05abcc3172bc5f9d94bb49edf6c
Tx public key: 488e818be1bbc133f28c931e095478def6cc53e64da47bf80d53b10831e0ec6e
Timestamp: 1707548507 Timestamp [UCT]: 2024-02-10 07:01:47 Age [y:d:h:m:s]: 01:067:00:40:21
Block: 954321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308953 RingCT/type: yes/0
Extra: 01488e818be1bbc133f28c931e095478def6cc53e64da47bf80d53b10831e0ec6e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bacec4438383d62323f934fdab1f820ef0460f9a8c6d2d2e20751278aa7cb86 0.600000000000 1413601 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": 954331, "vin": [ { "gen": { "height": 954321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bacec4438383d62323f934fdab1f820ef0460f9a8c6d2d2e20751278aa7cb86" } } ], "extra": [ 1, 72, 142, 129, 139, 225, 187, 193, 51, 242, 140, 147, 30, 9, 84, 120, 222, 246, 204, 83, 230, 77, 164, 123, 248, 13, 83, 177, 8, 49, 224, 236, 110, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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