Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 679fc214b3627c8adcab9cb413e24514c2dfd9b1514cd5679963f639277089c5

Tx prefix hash: fe0129c50e3d6150f754697e0f966b2d5b1fa1ec60e5d4f791e89527e40e8bc3
Tx public key: e58ec9a3622098e64bf1d0c53a6415f9c30f26d92214e2943d966bef32cc2730
Timestamp: 1746133970 Timestamp [UCT]: 2025-05-01 21:12:50 Age [y:d:h:m:s]: 00:275:19:17:05
Block: 1273697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194751 RingCT/type: yes/0
Extra: 01e58ec9a3622098e64bf1d0c53a6415f9c30f26d92214e2943d966bef32cc273002110000000ad8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a360320a78f575bf035e4c152519bcf5ec545eaca8ea9741aab07dbaaaa85302 0.600000000000 1760980 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": 1273707, "vin": [ { "gen": { "height": 1273697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a360320a78f575bf035e4c152519bcf5ec545eaca8ea9741aab07dbaaaa85302" } } ], "extra": [ 1, 229, 142, 201, 163, 98, 32, 152, 230, 75, 241, 208, 197, 58, 100, 21, 249, 195, 15, 38, 217, 34, 20, 226, 148, 61, 150, 107, 239, 50, 204, 39, 48, 2, 17, 0, 0, 0, 10, 216, 231, 210, 65, 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