Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6e15c28d6b51d843e26f00aec56e1fdf11e42ad81fba5c9c77791216f6b6e8e

Tx prefix hash: fc7f17281384108366db3b0d4c5b1c05ac3930d6643cdf4e3c9b7232a86046d0
Tx public key: dcfbc7043574767a4b4962ee067b819d6dbba3250d2c4b7b28889348f4c5d3b8
Timestamp: 1705385572 Timestamp [UCT]: 2024-01-16 06:12:52 Age [y:d:h:m:s]: 00:361:14:45:11
Block: 936361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258907 RingCT/type: yes/0
Extra: 01dcfbc7043574767a4b4962ee067b819d6dbba3250d2c4b7b28889348f4c5d3b802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e6d2b0e3e6297a4ab10fc055bdfe9ec99485713bbd38889ea32745b4b013a1e 0.600000000000 1394385 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": 936371, "vin": [ { "gen": { "height": 936361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e6d2b0e3e6297a4ab10fc055bdfe9ec99485713bbd38889ea32745b4b013a1e" } } ], "extra": [ 1, 220, 251, 199, 4, 53, 116, 118, 122, 75, 73, 98, 238, 6, 123, 129, 157, 109, 187, 163, 37, 13, 44, 75, 123, 40, 136, 147, 72, 244, 197, 211, 184, 2, 17, 0, 0, 0, 2, 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