Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e06cd694d9eac41b894b386546a34bfbafc576e42f4503304fab42347d023fc3

Tx prefix hash: dc654d3916108c4a0c68a7a7d4268d942905826081ff4d18cb31e998642c6a56
Tx public key: a3eee8fb1c954335cbf5a7287c33a8e68ebd9d937bdb559dda4f72164b85ee53
Timestamp: 1738851910 Timestamp [UCT]: 2025-02-06 14:25:10 Age [y:d:h:m:s]: 00:287:14:02:54
Block: 1213418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203282 RingCT/type: yes/0
Extra: 01a3eee8fb1c954335cbf5a7287c33a8e68ebd9d937bdb559dda4f72164b85ee5302110000000127ff1f91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de940936f8c846181ef8a1302a4cb7bcd5f865e3a926eb51fce1fd8787f0ce0d 0.600000000000 1700197 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": 1213428, "vin": [ { "gen": { "height": 1213418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de940936f8c846181ef8a1302a4cb7bcd5f865e3a926eb51fce1fd8787f0ce0d" } } ], "extra": [ 1, 163, 238, 232, 251, 28, 149, 67, 53, 203, 245, 167, 40, 124, 51, 168, 230, 142, 189, 157, 147, 123, 219, 85, 157, 218, 79, 114, 22, 75, 133, 238, 83, 2, 17, 0, 0, 0, 1, 39, 255, 31, 145, 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