Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3d263906cf195ed3bd996c77ded7f44571cca4998b22c07619a14e7216492fd

Tx prefix hash: e25eca81e1557a7fa64a4524b05d419323ec7b4bd7477b4ad3476e9deeb3675c
Tx public key: 51bcdc08398fdd7a3d2f7f0f7b428db0c54a06ce58c287c653a8462fd7176d23
Timestamp: 1726233620 Timestamp [UCT]: 2024-09-13 13:20:20 Age [y:d:h:m:s]: 00:131:14:33:11
Block: 1109230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94082 RingCT/type: yes/0
Extra: 0151bcdc08398fdd7a3d2f7f0f7b428db0c54a06ce58c287c653a8462fd7176d23021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56efa2f3963e565e9287b28368de338280b5a23978de9f5b9803e9c8bc3f74f9 0.600000000000 1587407 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": 1109240, "vin": [ { "gen": { "height": 1109230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56efa2f3963e565e9287b28368de338280b5a23978de9f5b9803e9c8bc3f74f9" } } ], "extra": [ 1, 81, 188, 220, 8, 57, 143, 221, 122, 61, 47, 127, 15, 123, 66, 141, 176, 197, 74, 6, 206, 88, 194, 135, 198, 83, 168, 70, 47, 215, 23, 109, 35, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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