Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feb4f5abcc361cd3009f905dfb55b0ea5a0042090baa2d44e539912c5d9bb9f2

Tx prefix hash: ade6b5e085e0a7c263b26a9c668074e85ef42723877c049155c802b776042734
Tx public key: 582b771b9a00a8443feafc440cfda9ac88e15c50c6e554d31e94a4e29aadf61d
Timestamp: 1707248892 Timestamp [UCT]: 2024-02-06 19:48:12 Age [y:d:h:m:s]: 01:273:20:14:10
Block: 951835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454474 RingCT/type: yes/0
Extra: 01582b771b9a00a8443feafc440cfda9ac88e15c50c6e554d31e94a4e29aadf61d02110000000710a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da10e3527179617c9ceb0f0de016e48c2143debce0352351654b1f23d4b6a2ad 0.600000000000 1410667 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": 951845, "vin": [ { "gen": { "height": 951835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da10e3527179617c9ceb0f0de016e48c2143debce0352351654b1f23d4b6a2ad" } } ], "extra": [ 1, 88, 43, 119, 27, 154, 0, 168, 68, 63, 234, 252, 68, 12, 253, 169, 172, 136, 225, 92, 80, 198, 229, 84, 211, 30, 148, 164, 226, 154, 173, 246, 29, 2, 17, 0, 0, 0, 7, 16, 161, 116, 143, 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