Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f108c5a01eb0115f5332d53582b77d78aef3d74f29776179bd5358d0614c08d

Tx prefix hash: 2fd0d2e33891831d7a925d92b56425886d592fba1450e2e7b99a801b65622880
Tx public key: eb0c5c08eb826a480e369d8b6b645a718a22ebd21eecee7f69e969e690a97c5d
Timestamp: 1703045499 Timestamp [UCT]: 2023-12-20 04:11:39 Age [y:d:h:m:s]: 01:107:19:59:38
Block: 916995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338189 RingCT/type: yes/0
Extra: 01eb0c5c08eb826a480e369d8b6b645a718a22ebd21eecee7f69e969e690a97c5d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f583aa8de1430951aee09cae0dc9933a255bb28ba11491a954052c5cbf5cff76 0.600000000000 1374559 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": 917005, "vin": [ { "gen": { "height": 916995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f583aa8de1430951aee09cae0dc9933a255bb28ba11491a954052c5cbf5cff76" } } ], "extra": [ 1, 235, 12, 92, 8, 235, 130, 106, 72, 14, 54, 157, 139, 107, 100, 90, 113, 138, 34, 235, 210, 30, 236, 238, 127, 105, 233, 105, 230, 144, 169, 124, 93, 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