Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef901933b690ead1051be3ceb174f9e779443a3de94582eeb68f9bb764c953e2

Tx prefix hash: b9fa755325e4ce6ef4e20be2a385160e7d7d4bca99b183d0223449faaaabe67a
Tx public key: 152e4da9fd0fece912f5679f6947541dfecf09ff67bd19c74ca6f2c641cabe1a
Timestamp: 1727636500 Timestamp [UCT]: 2024-09-29 19:01:40 Age [y:d:h:m:s]: 00:104:01:48:18
Block: 1120862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74403 RingCT/type: yes/0
Extra: 01152e4da9fd0fece912f5679f6947541dfecf09ff67bd19c74ca6f2c641cabe1a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 984a716462854afdb64ccf8f89f5f09327a4a2df4d3a8ea03c2fc23feb817fde 0.600000000000 1602933 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": 1120872, "vin": [ { "gen": { "height": 1120862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "984a716462854afdb64ccf8f89f5f09327a4a2df4d3a8ea03c2fc23feb817fde" } } ], "extra": [ 1, 21, 46, 77, 169, 253, 15, 236, 233, 18, 245, 103, 159, 105, 71, 84, 29, 254, 207, 9, 255, 103, 189, 25, 199, 76, 166, 242, 198, 65, 202, 190, 26, 2, 17, 0, 0, 0, 4, 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