Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e6dd05299ce012e790044e8219e5d917ddf7b0cb02816c10b0370c656f7ec56

Tx prefix hash: b53390d8c34ffebe7a828df18a06921eb61221c080e955374cb6b4cd0a445771
Tx public key: 3577325cfa1a08fa24b236bc4490a120977ceff09d14f2c7a331d4783d6450fb
Timestamp: 1705287695 Timestamp [UCT]: 2024-01-15 03:01:35 Age [y:d:h:m:s]: 01:084:04:41:03
Block: 935549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321284 RingCT/type: yes/0
Extra: 013577325cfa1a08fa24b236bc4490a120977ceff09d14f2c7a331d4783d6450fb0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56513214a396ae471af4f47cc306b97b9a7ead998a1cb8c6aa9fcbd4e94b1bef 0.600000000000 1393565 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": 935559, "vin": [ { "gen": { "height": 935549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56513214a396ae471af4f47cc306b97b9a7ead998a1cb8c6aa9fcbd4e94b1bef" } } ], "extra": [ 1, 53, 119, 50, 92, 250, 26, 8, 250, 36, 178, 54, 188, 68, 144, 161, 32, 151, 124, 239, 240, 157, 20, 242, 199, 163, 49, 212, 120, 61, 100, 80, 251, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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