Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f1460473882f030b4113e31af6865fd81a4be234fda2ff0a24ef71c39bf5e1e

Tx prefix hash: cfb044fb55ab9d7665794df88d2bec148989d8a9bee66eb9d7e6952d704bb2f4
Tx public key: 364f0149ae09ce0b378f9c8699f6e545f2b990f1a7e332c7f19dddbc4de5c2b4
Timestamp: 1698022210 Timestamp [UCT]: 2023-10-23 00:50:10 Age [y:d:h:m:s]: 01:093:01:39:47
Block: 875551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327713 RingCT/type: yes/0
Extra: 01364f0149ae09ce0b378f9c8699f6e545f2b990f1a7e332c7f19dddbc4de5c2b402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.770790046000 dcy

stealth address amount amount idx
00: 73677d54120a63699f5552c8293bfca8374239af6017c6fdbc97ff7c75e9d0a8 0.770790046000 1330811 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": 875561, "vin": [ { "gen": { "height": 875551 } } ], "vout": [ { "amount": 770790046, "target": { "key": "73677d54120a63699f5552c8293bfca8374239af6017c6fdbc97ff7c75e9d0a8" } } ], "extra": [ 1, 54, 79, 1, 73, 174, 9, 206, 11, 55, 143, 156, 134, 153, 246, 229, 69, 242, 185, 144, 241, 167, 227, 50, 199, 241, 157, 221, 188, 77, 229, 194, 180, 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