Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce690e9b78c95e341874109f37ed116606baa0c93b1e5f7f1d48095e0c92036

Tx prefix hash: f733049516346723ce05fbc7c0eafc09f57342f785dc2d011a3ee6202f0ffffd
Tx public key: a46d3302a645ba2c38e613d8e7e7a9c4aca7be75eae4cc954dab17ae2fbc3c93
Timestamp: 1671792360 Timestamp [UCT]: 2022-12-23 10:46:00 Age [y:d:h:m:s]: 02:067:08:05:30
Block: 658780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569770 RingCT/type: yes/0
Extra: 01a46d3302a645ba2c38e613d8e7e7a9c4aca7be75eae4cc954dab17ae2fbc3c9302110000000275e3f0e9000000000000000000

1 output(s) for total of 4.028917376000 dcy

stealth address amount amount idx
00: 473b0e6a80c933f88360836ad2f850b496763f7f0027d9e265fc07e2d8e392f4 4.028917376000 1099469 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": 658790, "vin": [ { "gen": { "height": 658780 } } ], "vout": [ { "amount": 4028917376, "target": { "key": "473b0e6a80c933f88360836ad2f850b496763f7f0027d9e265fc07e2d8e392f4" } } ], "extra": [ 1, 164, 109, 51, 2, 166, 69, 186, 44, 56, 230, 19, 216, 231, 231, 169, 196, 172, 167, 190, 117, 234, 228, 204, 149, 77, 171, 23, 174, 47, 188, 60, 147, 2, 17, 0, 0, 0, 2, 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