Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ae4d92d97e4c2dd8843f9908d8121ab37300c95d1d52cd94064839b6ac93e76

Tx prefix hash: 81249e7b8de9b40b3dc799071c87ca1eb912cb758322a72fbada1d2d71ce0ebe
Tx public key: 6a86f49f06b6fd98cee042372f226acd635e6b9f3eee68470bb0dda4fa30bc43
Timestamp: 1713844736 Timestamp [UCT]: 2024-04-23 03:58:56 Age [y:d:h:m:s]: 00:308:01:08:50
Block: 1006525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220186 RingCT/type: yes/0
Extra: 016a86f49f06b6fd98cee042372f226acd635e6b9f3eee68470bb0dda4fa30bc430211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f915ad886ecde87c855c8a286f6c1c1c256f8890ac587ae7db232a718153ee80 0.600000000000 1467583 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": 1006535, "vin": [ { "gen": { "height": 1006525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f915ad886ecde87c855c8a286f6c1c1c256f8890ac587ae7db232a718153ee80" } } ], "extra": [ 1, 106, 134, 244, 159, 6, 182, 253, 152, 206, 224, 66, 55, 47, 34, 106, 205, 99, 94, 107, 159, 62, 238, 104, 71, 11, 176, 221, 164, 250, 48, 188, 67, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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