Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f147948f7cf87e4f2d69067aef92af6a8fd5750651723a6de4691794be1a17c

Tx prefix hash: 1c1e41fd11675d93960c29d5e970ba7d9af52e77e12f6f69794eb6d349dc75bf
Tx public key: 84f2789f972f22b745d953f96c56e3ca86e979e68bebffe9d010accfad7fa6c8
Timestamp: 1715363847 Timestamp [UCT]: 2024-05-10 17:57:27 Age [y:d:h:m:s]: 00:247:08:16:05
Block: 1019120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177028 RingCT/type: yes/0
Extra: 0184f2789f972f22b745d953f96c56e3ca86e979e68bebffe9d010accfad7fa6c802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6eb7a9a06f6f009886e158de0f411efe85a1b52ee201ec0b1ad3cf3ddca8fe87 0.600000000000 1483007 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": 1019130, "vin": [ { "gen": { "height": 1019120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6eb7a9a06f6f009886e158de0f411efe85a1b52ee201ec0b1ad3cf3ddca8fe87" } } ], "extra": [ 1, 132, 242, 120, 159, 151, 47, 34, 183, 69, 217, 83, 249, 108, 86, 227, 202, 134, 233, 121, 230, 139, 235, 255, 233, 208, 16, 172, 207, 173, 127, 166, 200, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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