Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96a5171dad4260532c58e9dc676f8bdf7640cf9f3b2ac27bc3b21114a64858e9

Tx prefix hash: 5a585e7e225371c271cd8322f7d78c8bfb13bc717ace2a36d23361fba6c72adb
Tx public key: e7a5848cf53221180d0ba8b6c10c4a179ce8043506786706fcd775d0ee2b9d0a
Timestamp: 1745830437 Timestamp [UCT]: 2025-04-28 08:53:57 Age [y:d:h:m:s]: 00:013:01:44:05
Block: 1271187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9349 RingCT/type: yes/0
Extra: 01e7a5848cf53221180d0ba8b6c10c4a179ce8043506786706fcd775d0ee2b9d0a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1e9f496794a3136956b6737c32654d1d56dee90b3dc33a34030e4f1711aa035 0.600000000000 1758442 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": 1271197, "vin": [ { "gen": { "height": 1271187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1e9f496794a3136956b6737c32654d1d56dee90b3dc33a34030e4f1711aa035" } } ], "extra": [ 1, 231, 165, 132, 140, 245, 50, 33, 24, 13, 11, 168, 182, 193, 12, 74, 23, 156, 232, 4, 53, 6, 120, 103, 6, 252, 215, 117, 208, 238, 43, 157, 10, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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