Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 508e7c18921562b07fa8f582f1c35fc9179b39ed1925aa89410101e11f86430f

Tx prefix hash: 4ac4dd203e4b2880b7e0ce3c9ebac73a3163a0f6b9ab5d13a77257026447b17e
Tx public key: 36893dc0b4b5f4f841e2b37ae77135b51339cb2e0224eaf77cbc1eaa35d62223
Timestamp: 1659415472 Timestamp [UCT]: 2022-08-02 04:44:32 Age [y:d:h:m:s]: 02:252:07:48:56
Block: 556863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 701558 RingCT/type: yes/0
Extra: 0136893dc0b4b5f4f841e2b37ae77135b51339cb2e0224eaf77cbc1eaa35d622230211000000016570b1ef000000000000000000

1 output(s) for total of 8.767622417000 dcy

stealth address amount amount idx
00: 330d41800d77d4b4c4ad8a2704330e4c44e6a13bae47608d05fe52e031b9c040 8.767622417000 988819 of 0

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": 556873, "vin": [ { "gen": { "height": 556863 } } ], "vout": [ { "amount": 8767622417, "target": { "key": "330d41800d77d4b4c4ad8a2704330e4c44e6a13bae47608d05fe52e031b9c040" } } ], "extra": [ 1, 54, 137, 61, 192, 180, 181, 244, 248, 65, 226, 179, 122, 231, 113, 53, 181, 19, 57, 203, 46, 2, 36, 234, 247, 124, 188, 30, 170, 53, 214, 34, 35, 2, 17, 0, 0, 0, 1, 101, 112, 177, 239, 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