Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5755ccd28016b88964dc679080ed29a1ca2a419cb6fe37e1585a4ec0a24107e

Tx prefix hash: 347c12cf1e11f70d111c04d720a7f49f43ee011459c7a5a11c70f25765353c15
Tx public key: f4f23e02e3a2618c60e5c90651120a061aa322c380a786aa91c79cc43067a4b1
Timestamp: 1727764540 Timestamp [UCT]: 2024-10-01 06:35:40 Age [y:d:h:m:s]: 00:053:19:58:34
Block: 1121936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38460 RingCT/type: yes/0
Extra: 01f4f23e02e3a2618c60e5c90651120a061aa322c380a786aa91c79cc43067a4b1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24cac3a24f5c757cba46395ef03a387397b4e08a80c379f4bae47e90b3e0d59f 0.600000000000 1604299 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": 1121946, "vin": [ { "gen": { "height": 1121936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24cac3a24f5c757cba46395ef03a387397b4e08a80c379f4bae47e90b3e0d59f" } } ], "extra": [ 1, 244, 242, 62, 2, 227, 162, 97, 140, 96, 229, 201, 6, 81, 18, 10, 6, 26, 163, 34, 195, 128, 167, 134, 170, 145, 199, 156, 196, 48, 103, 164, 177, 2, 17, 0, 0, 0, 3, 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