Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1e5048ea71326c915a7b8fb25640cb14c56ed543747d6348c432389fec5ace4

Tx prefix hash: 22ee790cebeac5157f68dc1245173a5d724fd4c76fb8ece8a72fa90d2459b76c
Tx public key: 9fb8da95ab9e5bf89b7c48ccfa58695f44e4adc308a11d9d869428482c51dac4
Timestamp: 1705970310 Timestamp [UCT]: 2024-01-23 00:38:30 Age [y:d:h:m:s]: 01:143:18:42:26
Block: 941213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363825 RingCT/type: yes/0
Extra: 019fb8da95ab9e5bf89b7c48ccfa58695f44e4adc308a11d9d869428482c51dac402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad2442e50a4070245d0488a6a0010f9887bbdcfc1e6f25e498de088da26a38ef 0.600000000000 1399359 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": 941223, "vin": [ { "gen": { "height": 941213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad2442e50a4070245d0488a6a0010f9887bbdcfc1e6f25e498de088da26a38ef" } } ], "extra": [ 1, 159, 184, 218, 149, 171, 158, 91, 248, 155, 124, 72, 204, 250, 88, 105, 95, 68, 228, 173, 195, 8, 161, 29, 157, 134, 148, 40, 72, 44, 81, 218, 196, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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