Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27499797ccc40b12776b3d6aadc712af8999450f6297b8992788927c600e79d9

Tx prefix hash: 78aaa8a9354094b5b22eadab13d23fcb909d857679024fd7f9700bb856d05f53
Tx public key: 73b1898bd8ae1e54bdf7b9f2d31b2976ec5194f3e445b20f4ce9260d672be33f
Timestamp: 1709130735 Timestamp [UCT]: 2024-02-28 14:32:15 Age [y:d:h:m:s]: 01:114:09:11:19
Block: 967451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342621 RingCT/type: yes/0
Extra: 0173b1898bd8ae1e54bdf7b9f2d31b2976ec5194f3e445b20f4ce9260d672be33f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eca69d1c8e0e29e9fdda29cf5c642a3fada95c193a5807edc8c4901d4529e244 0.600000000000 1427230 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": 967461, "vin": [ { "gen": { "height": 967451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eca69d1c8e0e29e9fdda29cf5c642a3fada95c193a5807edc8c4901d4529e244" } } ], "extra": [ 1, 115, 177, 137, 139, 216, 174, 30, 84, 189, 247, 185, 242, 211, 27, 41, 118, 236, 81, 148, 243, 228, 69, 178, 15, 76, 233, 38, 13, 103, 43, 227, 63, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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