Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff3da56829fcb34c0d041838ef1a55cf6f7d61fbab5f7dbcafa464e6ab86709f

Tx prefix hash: d83b2a63fbab0a87f092bba241296caceec095290c412d6f1f04f9214920eb4f
Tx public key: 9d6614e6d0868b94bb418b4131dade21d4c5b39c41663b2a393f8f5fdf6e4916
Timestamp: 1740974397 Timestamp [UCT]: 2025-03-03 03:59:57 Age [y:d:h:m:s]: 00:262:21:33:56
Block: 1230974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185642 RingCT/type: yes/0
Extra: 019d6614e6d0868b94bb418b4131dade21d4c5b39c41663b2a393f8f5fdf6e49160211000000171f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 196e51d9795620770f5ae47de30f99d293ad109f234aa5ec808f6cd65000e18b 0.600000000000 1717877 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": 1230984, "vin": [ { "gen": { "height": 1230974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "196e51d9795620770f5ae47de30f99d293ad109f234aa5ec808f6cd65000e18b" } } ], "extra": [ 1, 157, 102, 20, 230, 208, 134, 139, 148, 187, 65, 139, 65, 49, 218, 222, 33, 212, 197, 179, 156, 65, 102, 59, 42, 57, 63, 143, 95, 223, 110, 73, 22, 2, 17, 0, 0, 0, 23, 31, 10, 83, 235, 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