Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa3022ca5e965a4b0f6a65e9042c498473dcb06c5c6c8ee8dddc12f6e6355a84

Tx prefix hash: d58613a03d4ad06a7cfee96f8f23f741078bca31251c39116549f3ebaf66b158
Tx public key: 8ec9d314b20efc85ac565611236cbc6ddc66e1f71e17cff1331a9dc9c110ca70
Timestamp: 1716727409 Timestamp [UCT]: 2024-05-26 12:43:29 Age [y:d:h:m:s]: 01:165:07:38:54
Block: 1030433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376733 RingCT/type: yes/0
Extra: 018ec9d314b20efc85ac565611236cbc6ddc66e1f71e17cff1331a9dc9c110ca7002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4edf2592cd1fd8c38bcad40ad2abaf9846d7445127dd709c3329969b2ccfd4a2 0.600000000000 1498688 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": 1030443, "vin": [ { "gen": { "height": 1030433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4edf2592cd1fd8c38bcad40ad2abaf9846d7445127dd709c3329969b2ccfd4a2" } } ], "extra": [ 1, 142, 201, 211, 20, 178, 14, 252, 133, 172, 86, 86, 17, 35, 108, 188, 109, 220, 102, 225, 247, 30, 23, 207, 241, 51, 26, 157, 201, 193, 16, 202, 112, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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