Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19d86efadb55a286ab429dcd8927f6d81f3db9cf041f6195a8c3865e4f857105

Tx prefix hash: 100f6bbcd2deb0224a2d8a6df954b9ce7e97024be79072d35e0c89e0a5a49ecd
Tx public key: b30710a0e0e723839d324d98ba989c2adf37bbe3e45de365a1c848faf43bcd51
Timestamp: 1699714139 Timestamp [UCT]: 2023-11-11 14:48:59 Age [y:d:h:m:s]: 01:154:09:49:14
Block: 889379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371562 RingCT/type: yes/0
Extra: 01b30710a0e0e723839d324d98ba989c2adf37bbe3e45de365a1c848faf43bcd5102110000000375e3f0e9000000000000000000

1 output(s) for total of 0.693614515000 dcy

stealth address amount amount idx
00: b36ffd74c0cc9b7f4b9ee79cb1b77bbc24387d05d13cb11b554b64c5128fdcc4 0.693614515000 1345376 of 0

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": 889389, "vin": [ { "gen": { "height": 889379 } } ], "vout": [ { "amount": 693614515, "target": { "key": "b36ffd74c0cc9b7f4b9ee79cb1b77bbc24387d05d13cb11b554b64c5128fdcc4" } } ], "extra": [ 1, 179, 7, 16, 160, 224, 231, 35, 131, 157, 50, 77, 152, 186, 152, 156, 42, 223, 55, 187, 227, 228, 93, 227, 101, 161, 200, 72, 250, 244, 59, 205, 81, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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