Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bbed8ea9a002d9ff51900e179ebc75182ab573edd02932f1a96787329f9bc3a

Tx prefix hash: b462ec7f50eb1a5768cb6d667737cc564893e7fe96280a7e29faf9081e63e142
Tx public key: 785d3d289d65899053ec84d58be04a44acc933a9a0e9869e6ca0a5e0af1d332a
Timestamp: 1684420737 Timestamp [UCT]: 2023-05-18 14:38:57 Age [y:d:h:m:s]: 01:239:23:15:45
Block: 762840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432942 RingCT/type: yes/0
Extra: 01785d3d289d65899053ec84d58be04a44acc933a9a0e9869e6ca0a5e0af1d332a02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.821404967000 dcy

stealth address amount amount idx
00: f3f468fcd4e379c1c6501222cf74adcb61fb68c1b83456205b8aea564295c03a 1.821404967000 1211615 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": 762850, "vin": [ { "gen": { "height": 762840 } } ], "vout": [ { "amount": 1821404967, "target": { "key": "f3f468fcd4e379c1c6501222cf74adcb61fb68c1b83456205b8aea564295c03a" } } ], "extra": [ 1, 120, 93, 61, 40, 157, 101, 137, 144, 83, 236, 132, 213, 139, 224, 74, 68, 172, 201, 51, 169, 160, 233, 134, 158, 108, 160, 165, 224, 175, 29, 51, 42, 2, 17, 0, 0, 0, 1, 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