Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a31123bc7ac67e541f38bd778b0332573d8ffb71f41c22dedf0c2fb4ef21b91f

Tx prefix hash: e3ab0ce7c9dec926331325e99443d6655493e9534a5311a5192325c92aaf8f29
Tx public key: d7cb0ed0a1727b30c9524504c504294be1d5e508ea840acb7f0bf0b4fe41ba35
Timestamp: 1740934468 Timestamp [UCT]: 2025-03-02 16:54:28 Age [y:d:h:m:s]: 00:103:11:14:00
Block: 1230643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73941 RingCT/type: yes/0
Extra: 01d7cb0ed0a1727b30c9524504c504294be1d5e508ea840acb7f0bf0b4fe41ba35021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 514f2bb574171d2775c07f00361dc2e4cece03dff556864eb7b16d878aafbde7 0.600000000000 1717542 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": 1230653, "vin": [ { "gen": { "height": 1230643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "514f2bb574171d2775c07f00361dc2e4cece03dff556864eb7b16d878aafbde7" } } ], "extra": [ 1, 215, 203, 14, 208, 161, 114, 123, 48, 201, 82, 69, 4, 197, 4, 41, 75, 225, 213, 229, 8, 234, 132, 10, 203, 127, 11, 240, 180, 254, 65, 186, 53, 2, 17, 0, 0, 0, 2, 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