Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4791ac48c1a9404d0e82072a26424c7e67bdf9a5b2a15ad3732116d819e79de

Tx prefix hash: c6f6429cda1bb7e9c02d4645302479b8be2f5582160e6c7aef3c8f7ece2d575b
Tx public key: fc69a88985a4208d33e887d75d9e550bc6fa9639080d9d2bea096984a7e35f07
Timestamp: 1735748823 Timestamp [UCT]: 2025-01-01 16:27:03 Age [y:d:h:m:s]: 00:168:16:07:06
Block: 1187988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120248 RingCT/type: yes/0
Extra: 01fc69a88985a4208d33e887d75d9e550bc6fa9639080d9d2bea096984a7e35f07021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 593b2f671db8d9b0be8357325025eab877b6692382bdc7df1822c90041c5b802 0.600000000000 1674487 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": 1187998, "vin": [ { "gen": { "height": 1187988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "593b2f671db8d9b0be8357325025eab877b6692382bdc7df1822c90041c5b802" } } ], "extra": [ 1, 252, 105, 168, 137, 133, 164, 32, 141, 51, 232, 135, 215, 93, 158, 85, 11, 198, 250, 150, 57, 8, 13, 157, 43, 234, 9, 105, 132, 167, 227, 95, 7, 2, 17, 0, 0, 0, 2, 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