Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2b4e4bfba0d1ee0143358fbd382f88a03099c1f509ddf024e37f6a677a00f13

Tx prefix hash: 3d1f7e266738f098d9ce0c312a120a42060216a45ea939363aed94cf715b3baa
Tx public key: f78c006e6dbac33fef535cf03a3e42941683f35bf0a90b470f29666913f30d44
Timestamp: 1632392152 Timestamp [UCT]: 2021-09-23 10:15:52 Age [y:d:h:m:s]: 03:096:18:27:18
Block: 339381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 845389 RingCT/type: yes/0
Extra: 01f78c006e6dbac33fef535cf03a3e42941683f35bf0a90b470f29666913f30d44021100000044f60c5d7e000000000000000000

1 output(s) for total of 46.078447317000 dcy

stealth address amount amount idx
00: 056e1b52f20155e4c635ae7b17031727e88a25dd93ebf01c94f94e62b7d3a9e2 46.078447317000 698010 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": 339391, "vin": [ { "gen": { "height": 339381 } } ], "vout": [ { "amount": 46078447317, "target": { "key": "056e1b52f20155e4c635ae7b17031727e88a25dd93ebf01c94f94e62b7d3a9e2" } } ], "extra": [ 1, 247, 140, 0, 110, 109, 186, 195, 63, 239, 83, 92, 240, 58, 62, 66, 148, 22, 131, 243, 91, 240, 169, 11, 71, 15, 41, 102, 105, 19, 243, 13, 68, 2, 17, 0, 0, 0, 68, 246, 12, 93, 126, 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