Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be08ccd39e7e265c430f910d5f62501509a42f5efe66b2d5a50add6b4e470c06

Tx prefix hash: c74cd08dee84760dbe0cf7bda03e565261207ec154b860f1380f373e1dc3dff5
Tx public key: d5ea600306c568a56b5c0442138abc46926408146c1d6b979ac23564e50aa5b1
Timestamp: 1729357103 Timestamp [UCT]: 2024-10-19 16:58:23 Age [y:d:h:m:s]: 00:035:22:53:02
Block: 1135122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25673 RingCT/type: yes/0
Extra: 01d5ea600306c568a56b5c0442138abc46926408146c1d6b979ac23564e50aa5b1021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a1c68d979dd9619f7f7900cd0da3a4b7d19227727ccf07462e5e241ceb2d22e 0.600000000000 1618453 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": 1135132, "vin": [ { "gen": { "height": 1135122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a1c68d979dd9619f7f7900cd0da3a4b7d19227727ccf07462e5e241ceb2d22e" } } ], "extra": [ 1, 213, 234, 96, 3, 6, 197, 104, 165, 107, 92, 4, 66, 19, 138, 188, 70, 146, 100, 8, 20, 108, 29, 107, 151, 154, 194, 53, 100, 229, 10, 165, 177, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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