Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 540c148d2f953e816a5b493d7998f55d62000b246ba0bef1b38085eb8839f6b7

Tx prefix hash: 2fbe8a618846e5f366e662d3167814acd68bc951a388533ae30b5ab1fba5fb70
Tx public key: 4e4c12dc99aa810873afcf1a43223cc8513c0647f1cd1ba1b1ce84aa605beca0
Timestamp: 1735724371 Timestamp [UCT]: 2025-01-01 09:39:31 Age [y:d:h:m:s]: 00:317:08:34:59
Block: 1187784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224331 RingCT/type: yes/0
Extra: 014e4c12dc99aa810873afcf1a43223cc8513c0647f1cd1ba1b1ce84aa605beca0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c4f677bae1545cbf5f7afd00028f9044954d39ee1405b1359163c8f34e4535a 0.600000000000 1674281 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": 1187794, "vin": [ { "gen": { "height": 1187784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c4f677bae1545cbf5f7afd00028f9044954d39ee1405b1359163c8f34e4535a" } } ], "extra": [ 1, 78, 76, 18, 220, 153, 170, 129, 8, 115, 175, 207, 26, 67, 34, 60, 200, 81, 60, 6, 71, 241, 205, 27, 161, 177, 206, 132, 170, 96, 91, 236, 160, 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