Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04978d0023573748119e8891717e742ad18e00fea5ccb211e80232a1c5babaaa

Tx prefix hash: 0f9855fb2bd76c0f56a877687afd9f4d7f0d8d2d8540b0d486350b6bd046cff2
Tx public key: 2f8d8d4a5079b21ab618df68f5201c5b0af0be78f5b2830f5063059684b135fd
Timestamp: 1738041772 Timestamp [UCT]: 2025-01-28 05:22:52 Age [y:d:h:m:s]: 00:327:09:34:40
Block: 1206730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231775 RingCT/type: yes/0
Extra: 012f8d8d4a5079b21ab618df68f5201c5b0af0be78f5b2830f5063059684b135fd0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b10f5402e3607c227fcc97971161bf1f27758b36b1020736ef008c83d37e0ffe 0.600000000000 1693443 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": 1206740, "vin": [ { "gen": { "height": 1206730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b10f5402e3607c227fcc97971161bf1f27758b36b1020736ef008c83d37e0ffe" } } ], "extra": [ 1, 47, 141, 141, 74, 80, 121, 178, 26, 182, 24, 223, 104, 245, 32, 28, 91, 10, 240, 190, 120, 245, 178, 131, 15, 80, 99, 5, 150, 132, 177, 53, 253, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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