Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 587b157e608f4243275b961e539d325d542da5592aef9491fa833a29bea52b2b

Tx prefix hash: 3d15e02d57e5655814c6495f0924b441c421d9b98622ca4a878f2e626a37f8a5
Tx public key: 88874ee228b0e3ba49bf372f2da4c8be2d0a69883cd83ea73fddb9f2e996890a
Timestamp: 1707217199 Timestamp [UCT]: 2024-02-06 10:59:59 Age [y:d:h:m:s]: 00:343:17:43:47
Block: 951574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246074 RingCT/type: yes/0
Extra: 0188874ee228b0e3ba49bf372f2da4c8be2d0a69883cd83ea73fddb9f2e996890a02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f987616b14b8476a0f078ca12ca85ea9cd8a8b5c4276a4358388c77edc83be2b 0.600000000000 1410356 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": 951584, "vin": [ { "gen": { "height": 951574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f987616b14b8476a0f078ca12ca85ea9cd8a8b5c4276a4358388c77edc83be2b" } } ], "extra": [ 1, 136, 135, 78, 226, 40, 176, 227, 186, 73, 191, 55, 47, 45, 164, 200, 190, 45, 10, 105, 136, 60, 216, 62, 167, 63, 221, 185, 242, 233, 150, 137, 10, 2, 17, 0, 0, 0, 7, 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