Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3352f1ef96eec57fec3f3931dd78f151078c4cad11720c1f19d9f44a606430ac

Tx prefix hash: cf833d7a484286e52797f4fac2e106d97470035ab8bc06bc7f70237e359167b5
Tx public key: bc1a38232e2c8f0340a2f9c6bc8c0f5b265d3de13d86acaba04ca16c6ef8a728
Timestamp: 1703535924 Timestamp [UCT]: 2023-12-25 20:25:24 Age [y:d:h:m:s]: 01:140:10:40:33
Block: 921063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361517 RingCT/type: yes/0
Extra: 01bc1a38232e2c8f0340a2f9c6bc8c0f5b265d3de13d86acaba04ca16c6ef8a72802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c4b7dbc84f7d44d90a66be074b51cc19fd72eb5ce95055ec3b72eff5c4635e6 0.600000000000 1378747 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": 921073, "vin": [ { "gen": { "height": 921063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c4b7dbc84f7d44d90a66be074b51cc19fd72eb5ce95055ec3b72eff5c4635e6" } } ], "extra": [ 1, 188, 26, 56, 35, 46, 44, 143, 3, 64, 162, 249, 198, 188, 140, 15, 91, 38, 93, 61, 225, 61, 134, 172, 171, 160, 76, 161, 108, 110, 248, 167, 40, 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