Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e91853b716bf6093654ee2f229fe7e160017b4f9ff52e184cadedd36637974b3

Tx prefix hash: a95456a87560e37ffb6ac86081d988a859c48f77d15b3123775e2c693f2d3519
Tx public key: 5fa1f9e9a74ad3fff0a17e1bbd8a415f1a303f3f61dbe89fab98a707823f4665
Timestamp: 1751070816 Timestamp [UCT]: 2025-06-28 00:33:36 Age [y:d:h:m:s]: 00:138:23:24:39
Block: 1314169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97408 RingCT/type: yes/0
Extra: 015fa1f9e9a74ad3fff0a17e1bbd8a415f1a303f3f61dbe89fab98a707823f4665021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ca784954eb540c336cd26cb30c78e1423fd19617f2ce31d7d2cf57a40aa1075 0.600000000000 1801814 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": 1314179, "vin": [ { "gen": { "height": 1314169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ca784954eb540c336cd26cb30c78e1423fd19617f2ce31d7d2cf57a40aa1075" } } ], "extra": [ 1, 95, 161, 249, 233, 167, 74, 211, 255, 240, 161, 126, 27, 189, 138, 65, 95, 26, 48, 63, 63, 97, 219, 232, 159, 171, 152, 167, 7, 130, 63, 70, 101, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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